Version 1.0 | Playwright + TypeScript | Completed / Portfolio Ready
| Item | Value |
|---|---|
| Project | Playwright-ParaBank-Automation |
| Version | 1.0.0 |
| Framework | Playwright + TypeScript |
| Application | ParaBank demo banking application |
| Status | Completed / Portfolio Ready |
| Scope | 70 mapped functional/security automation cases + framework demonstrations |
This project is a professional end-to-end UI automation framework for the ParaBank demo banking application. It demonstrates maintainable Playwright engineering practices rather than only individual browser scripts.
Additional framework demonstrations are kept separate from the 70 mapped cases:
DD001_invalid_passwords.spec.ts — data-driven authentication examples.DD002_username_boundary.spec.ts — data-driven username boundary examples.Find_Username_Boundary.spec.ts — exploratory investigation supporting the username boundary decision.allure-playwrightBasePage.The framework targets a locally hosted ParaBank instance using:
http://localhost:8081/parabank/
The application is a demo system and does not always behave like a production banking application. Some negative/validation scenarios expose application defects or misleading responses. These are intentionally preserved as QA findings rather than changing assertions merely to obtain a green run.
The CI workflow is configured, but a GitHub runner requires a ParaBank instance reachable from the runner before the full UI suite can execute successfully. The workflow configuration is therefore documented as infrastructure-ready rather than claiming a verified remote application environment.
The planned automation framework scope is implemented. Remaining improvements are optional portfolio enhancements and are not required to consider the project complete.
Future work may include Dockerized ParaBank execution, broader browser projects, richer CI publication, and additional portfolio presentation. These are optional enhancements and are outside the completed baseline.